In DOORS 8.3 we have a current module with incoming links from a baseline of a different module. The incoming links from the baseline prevent objects in the current module from being deleted. Is there any way around this?
David_G_Bond - Mon Feb 28 08:46:24 EST 2011 |
|
Re: Link from baselined module preventing deletion of object
Mathias Mamsch - Mon Feb 28 10:27:10 EST 2011
Odd situation. We could fix this on database level (specifically removing the broken link from the inlinks.dtc of the module).
Or you could try the following procedure:
-
Make a backup of the module's folder in the database
-
rename the inlinks.dtc file in the folder on the database
-
open the module (all in links should be gone!), purge the object, save and close.
-
rename the old inlinks.dtc back (in case DOORS created another one,delete that one).
If something goes wrong, restore the module from the backup.
You could also backup the source module completly on the server (including all baselines), delete the baseline with the link, open your module, purge the object and then restore the module with the baseline.
You could also try stuff like hiding the link module and the source module for a user, then trying to delete the object with that user. Mail me for a correction on database level (mmamsch at goole mail. com)
Maybe that helps, Regards, Mathias
Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS
|
|
Re: Link from baselined module preventing deletion of object
llandale - Mon Feb 28 16:13:43 EST 2011
Perhaps I'm overly paranoid, but mucking in the database folder hierarchy is ill advised.
Get an admin to deny you any "Read" rights to the link module in question; and possibly from the original source module. You should then be able to delete the object. Then have the admin restore your rights.
I think.
|
|
Re: Link from baselined module preventing deletion of object
Mathias Mamsch - Mon Feb 28 17:35:55 EST 2011 llandale - Mon Feb 28 16:13:43 EST 2011
Perhaps I'm overly paranoid, but mucking in the database folder hierarchy is ill advised.
Get an admin to deny you any "Read" rights to the link module in question; and possibly from the original source module. You should then be able to delete the object. Then have the admin restore your rights.
I think.
Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS
|
|
Re: Link from baselined module preventing deletion of object
SystemAdmin - Mon Feb 28 18:36:38 EST 2011
This problem was reported before - but a long time ago.
I have attached a screen grab from the old Telelogic forums where this was reported back in 2007 - in summary, it could be the result of a Baseline Set that is still open, or a corrupted Baseline Set. If it's a corruption, one of the respondents, Brian Azelborn, has an alternative method to fix at the database level, but best to check first if any Baseline Sets are open and can be closed off, or try Louie's suggestion in this forum before getting medieval with database files.
Paul Miller
Melbourne, Australia
Attachments
attachment_14588489_TelelogicForum_-_Delete_outgoing_links_f.png
|
|
Re: Link from baselined module preventing deletion of object
llandale - Mon Feb 28 18:49:37 EST 2011 Mathias Mamsch - Mon Feb 28 17:35:55 EST 2011
Ok Louie I have to ask this: If your module needed clever fixing, who would you rather trust: Me or IBM Support? ;-) Just kidding ... You are perfectly right, resorting to database level, should be the done, after all the other ways failed ... Lets hope that hiding the link module will work ... Regards, Mathias
Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS
Mom is right: its best not to play with "unloaded" guns.
Uncle Surgeon is right: there's more than just "knowing" what to do, there is also "skill".
And I'm right: there is no substitute for "experience".
And Dad is right: the only thing worse than playing with "unloaded" guns is being next such a guy.
|
|
Re: Link from baselined module preventing deletion of object
David_G_Bond - Tue Mar 01 14:44:06 EST 2011 llandale - Mon Feb 28 18:49:37 EST 2011
Well, if you were HERE I would certainly trust you to do whatever you thought, to heck with me and IBM support. Confidence drops drastically when it comes to you being THERE telling ME what exactly to do, when it comes to DB file manipulation.
Mom is right: its best not to play with "unloaded" guns.
Uncle Surgeon is right: there's more than just "knowing" what to do, there is also "skill".
And I'm right: there is no substitute for "experience".
And Dad is right: the only thing worse than playing with "unloaded" guns is being next such a guy.
Thank you for all of your suggestions. I work mostly with dxl and am only an occasional administrator. I've never had to deal with baseline sets before.
|
|
Re: Link from baselined module preventing deletion of object
llandale - Tue Mar 01 16:33:04 EST 2011 David_G_Bond - Tue Mar 01 14:44:06 EST 2011
The suggestion by Louie to create a user that does not have any access to the link module or source module did not work. DOORS was smart enough to know that there were links even though the current user could not see them. We decided to delete the baseline with the source links. When we tried DOORS created an error message saying that the baseline could not be deleted because it was part of an open baseline set. Being totally unfamiliar with baseline sets we mucked around until we found a dialog box that listed the baseline set along with a "Close" button. When we closed the baseline set, the incoming links from the baseline went away. This will probably fix the problem, but we have a change process that needs to be followed and as I am unfamiliar with it I will let the appropriate user verify that the problem is fixed.
Thank you for all of your suggestions. I work mostly with dxl and am only an occasional administrator. I've never had to deal with baseline sets before.
|
|
Re: Link from baselined module preventing deletion of object
David_G_Bond - Wed Mar 02 15:09:43 EST 2011 llandale - Tue Mar 01 16:33:04 EST 2011
Did you say that closing the Baseline Set resolved the problem, without having to delete the baseline?
|
|
